Still can't find what you're looking for?Known Issues
A known issue in Guardian is a problem or defect that has been identified by (or raised to) the Guardian Support Team that is being actively monitored and investigated. Whilst the issue is in review, it will be documented here for visibility. Until a solution is implemented, a temporary workaround may be made available. Once a solution has been implemented and 'Working as Expected' for 12 months, it will be moved to a 'Closed' state and then archived. The following page provides an overview of the known issues in Guardian.
Tip: If you have encountered an issue and would like to report it, you can Submit an Issue or email helpdesk@cloudhouse.com directly.
| Description | Status | Found in Release | Last Updated |
|---|---|---|---|
| KI.GWB.5900 – Files and Node Groups in Scan Options Issues | Workaround Available | V3.43.0 | 6th June 2024 |
|
KI.GWB.5915 – Database Disk Space Not Being Properly Calculated |
Working as Expected | V3.41.2 | 6th June 2024 |
|
KI.GWB.5946 – Unable to Add New AWS Integration without Internet Access |
Working as Expected | V3.35.2 | 5th June 2024 |
|
KI.GWB.6011 – Editing an AWS Node's Settings Results in Node Scan Failure |
Working as Expected | V3.47.2 | 12th November 2024 |
| KI.GWB.6014 – Excessive Load Times for Node Data Requests | Working as Expected | V3.47.3, V3.48.0 | 21st November 2024 |
| KI.GWB.6024 – Email Report Fails Using SMTP 'None' Auth Type | Working as Expected | V3.46.0 | 24th September 2024 |